release/1.5.0: site updates part 1 (Orion, Hercules, Narwhal) #770
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-3.10.8-6pvtcn2/lib/python3.10/distutils/unixccompiler.py and envs/unified-env-gcc-10.3.0/install/gcc/10.3.0/python-3.10.8-6pvtcn2/lib/python3.10/distutils/unixccompiler.py.dom.test
…m/climbfuji/spack-stack into feature/rel150_site_config_update_1
…ion errors with [email protected] and later and to avoid segmentation faults with ufs-weather-model
… of https://github.com/climbfuji/spack-stack into feature/release150_site_updates_orion_hercules_narwhal
3 tasks
…o different partition to avoid disk space issues
…into feature/release150_site_updates_part1_orion_hercules_narwhal
configs/sites/hercules/packages.yaml
Outdated
Comment on lines
26
to
28
| py-pyyaml: | ||
| require: | ||
| - "@5.4.1" |
There was a problem hiding this comment.
How critical is it for awscli to be the latest version? As I mentioned in my Slack message, I ran into the problem of conflicting awscli/py-pyyaml/py-botocore versions, and was able to resolve it by taking awscli and py-pyyaml back a version from the latest.
There was a problem hiding this comment.
Based on the slack conversation we had, shall we merge this as is or should I change py-pyyaml to 5.4.1 and set awscli accordingly (which version is it), and remove the extra settings for Hercules/Orion?
There was a problem hiding this comment.
If it works for all systems to set the versions in common/packages.yaml (py-pyyaml 5.4.1, awscli 1.27.84) then let's go ahead and do that.
ulmononian
approved these changes
Sep 12, 2023
climbfuji
deleted the
feature/release150_site_updates_part1_orion_hercules_narwhal
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
.github/workflows/macos-ci-aarch64.yaml- write spack caches to different partition (via a symbolic link) to avoid disk space issuesTesting
Applications affected
All applications on these three systems using spack-stack-1.5.0
Systems affected
Orion, Narwhal, Hercules
Dependencies
Issue(s) addressed
Checklist